Raise compileSdk to 37 to fix AAR-metadata check failure#335
Merged
Conversation
CI's checkReleaseAarMetadata task failed on android-llmservice:
activity-compose 1.13.0 / androidx.core 1.18.0 / navigationevent 1.0.0
require compileSdk >= 36, and lifecycle-{viewmodel,runtime}-compose
2.11.0 require compileSdk >= 37 — all pulled in by the dependency
bumps in #331. Raises compileSdk from 35 to 37 in
android-llmservice/app/build.gradle.kts (targetSdk is left at 35 on
purpose: compileSdk only widens the compile-time API surface,
targetSdk opts into new runtime behavior and is bumped independently).
Also bumps .github/android-consumer-test's compileSdk to stay in sync
with the fixture it mirrors, though it isn't independently required
there (no Compose dependency).
Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015qu2VUdHXRhp6ndxJGkxri
bernardladenthin
had a problem deploying
to
maven-central
July 11, 2026 13:23 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
July 11, 2026 13:23 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
July 11, 2026 13:23 — with
GitHub Actions
Error
GitHub Actions
Error
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
android-llmservice's:app:checkReleaseAarMetadatatask failed in CI with 9 AAR-metadata issues:activity-compose:1.13.0,androidx.core:1.18.0, andandroidx.navigationevent:*:1.0.0requirecompileSdk >= 36;lifecycle-{viewmodel,runtime}-compose:2.11.0requirecompileSdk >= 37. These versions were all pulled in by the dependency bumps in Upgrade AGP to 9.2.0 and Gradle to 9.4.1; update dependencies #331; the project was still oncompileSdk = 35.compileSdkfrom 35 to 37 inandroid-llmservice/app/build.gradle.kts.targetSdkis deliberately left at 35 —compileSdkonly widens the compile-time API surface,targetSdkopts into new runtime behavior and can be bumped independently (per AGP's own recommendation in the error output)..github/android-consumer-test'scompileSdkto stay in sync with the fixture it mirrors (not independently required there — that fixture has no Compose dependency).CLAUDE.mdnote.Test plan
:app:checkReleaseAarMetadatainbuild-android-llmserviceRelated issues / PRs
Follow-up to #331 (Compose/activity/lifecycle dependency bumps).
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdhttps://claude.ai/code/session_015qu2VUdHXRhp6ndxJGkxri
Generated by Claude Code